|
Move CH2 to NY4 Data Center |
Move NY4 to CH2 Data Center |
|
1) Suspend Trading, Notify Industry 2) Move Opcon (OCS, BLOC) for monitoring See Application Specific Recoveries 3) Move Instrument/System Activity loading (ISAR, DLAC) for ME See Application Specific Recoveries 4) Move Matching Engines (ME, TXR, DLME) for trading See Application Recovery - ME.docx 5) Move Market Data (QRS, TRS, BFS) for SIP and BFD reporting See Application Recovery - OMD.docx 6) Move Clearing (CLR, DTCC) for clearing See Application Specific Recoveries 7) Move Firm Comm (OMS, OMSB, DCSR, DTRF) See Application Specific Recoveries 8) Move Brokerplex and Administrative (BPLX, CSI, MNT, MROL) See Application Specific Recoveries 9) Move CMA (CMA, DPB, FSD) See Application Recovery - CMA.docx 10) Move BookFeed Retrans and Killswitch (BFDR, KSP, CHXG) See Application Specific Recoveries 11) Move database loaders (DLBF, DLBP, DLCM, DLCS, DLKS, DLMP, DLOM, DLQR, DLRT, DLTR) See Application Recovery - DBL XML.docx 12) Perform System Integrity Checks See CHX System Integrity Checklist.docx 13) Resume Trading, Notify Industry 14) Notify PTT for post trading impacts and resolutions. NOTE: If CH2 moves to NY4: - Brokerplex will lose access to AMD, BDC and RDC processes and related functionality. FSD access will be limited to those firms connecting in NY4 data center. - Order sending firms without redundant connectivity in NY4 will not have access to Matching Engines. They will also lose DCSF drop copies. |
1) Suspend Trading, Notify Industry 2) Move Matching Engines (ME, TXR, DLME) for trading See Application Recovery - ME.docx 3) Move Market Data (QRS, TRS, BFS) for SIP reporting See Application Recovery - OMD.docx 4) Move Firm Comm (OMS, DCSR) See Application Specific Recoveries 5) Move CMA (CMA, DPB, FSD) See Application Recovery - CMA.docx 6) Move database loaders (BLFM, DLBF, DLCM, DLMP, DLOM, DLQR, DLTR, FMR) See Application Recovery - DBL XML.docx and Application Recovery - DBL Binary.docx 7) Perform System Integrity Checks See CHX System Integrity Checklist.docx 8) Resume Trading, Notify Industry NOTE: If NY4 moves to CH2: - Order sending firms without redundant connectivity in NY4 will not have access to Matching Engines. They will also lose DCSF drop copies. |
The following applications do not move between Data Centers;
Either the data is replicated in the other data center or external sources are responsible for providing redundancy:
- MARKET DATA PROCESSORS / INBOUND MARKET DATA READERS (CQS, CTS, UQDF, UTDF)
o Data is redundantly read in both data centers.
- MARKET DATA LOADERS / INBOUND MARKET DATA LOADERS (BBOL, LSMR, QMTL, BLBD, BLLM, BLQM)
o Data is redundantly loaded in both data centers.
o PTT will need to account for using data out of one data center or the other.
- FIRM COMMUNICATIONS (AMD, BDC, DCSF, DPB, FSD, RDC)
o Firms are responsible for providing connectivity in both data centers.
o AMD, BDC, DCSF and RDC are only running in CH2.
- BROKER BACK OFFICE (CWAS, CWDP, CWFS, CWRG, CWTM))
o Broker Back Office Functionality is provided redundantly in both data centers.
o IBs will need to use client links facilitating use out of one data center or the other.
- BOOKFEED READER (BFRD)
o CHX Bookfeed data is multicast redundantly in both data centers.
o CHX Operations are the only users of Bookfeed Readers.
- UME DATA STORES (FIRM COMM AND OMD)
o UME data stores are separated between data centers.
o UME data senders and receivers are limited to data center specific store storage and retrieval.
- NESPR NAME SERVICE (NSPR)
o NESPR facilities exist in both data centers redundantly.
o CHX applications only require one instance of NESPR .